home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
JCSM Shareware Collection 1996 September
/
JCSM Shareware Collection (JCS Distribution) (September 1996).ISO
/
prgtools
/
sdnkit12.zip
/
SYSOP.TXT
< prev
next >
Wrap
Text File
|
1996-01-23
|
14KB
|
350 lines
SDN INTERNATIONAL(sm)
Shareware Distribution Network
Sysop Kit - Revision #12
Simple Guidelines For Receiving SDN Distribution
Published by The SDN Project, January 23rd 1996
(c)Copyright 1996 Ray L. Kaliss - The SDN Project
This document is Copyright The SDN Project 1996 and the property of
Ray L. Kaliss as The SDN Project.
This document in not public domain. It is intended as an
informational document for Bulleting Board Sysops considering
distribution via SDN International. This document may be copied
whole and unmodified for that intent only.
Official Policy is formulated by SDN International and published at
The SDN Project Bulletin Board in Meriden, CT, U.S.A.
203-634-0370. Policy posted online at The SDN Project supersedes
policy in circulation or of earlier date.
-= Copyright Notice =-
SDN, The SDN Project, and the service mark of SDN International are
Copyright 1989-1996 by Ray L. Kaliss and can not be used with out
express written permission. Files distributed by SDN are copyright
by their respective authors. The packaging format and SDN.ID
format are copyrighted by Ray L. Kaliss.
1. THE SDN PROJECT
~~~~~~~~~~~~~~~~~~
The SDN Project is the head quarters of SDN International(sm), the
Shareware Distribution Network for DOS, Windows and OS/2 shareware
programs. SDN embodies a concept of author, sysop and user
cooperation through the shareware concept in service to the
amateur, commercial amd Internet communication communities.
Beginning operations in January 1989, in Fidonet SDN is a public
service, gratis, with it's origin and organizational center at The
SDN Project BBS 1:141/840. It was the first and is the largest
author-direct distribution network of it's kind. SDN is a founding
member of the International File Distribution Cooperative (IFDC)
and the FileGate.
Shareware programs distributed via SDN are copyrighted works of
respective authors and can not be changed in anyway. The
copyrights of the individual authors are to be respected.
2. REASONS FOR SDN DISTRIBUTION
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As a bulletin board sysop, how many times in the past have you run
across these problems and wished there was a better way?
- Users upload programs with files missing.
- Uploaded programs have already been configured by someone.
- A new upload is really a five year old program.
- Users report a download from your board trashed his hard drive.
- Kids downloaded pornography you didn't even know was there.
- Foreign callers are downloading encryption that the US Government
says is illegal for you to make available to them.
- Someone posted a copy of dBase(tm) retail software as HOT-ONE.ARC
- Your posted version is an author's beta that he posted on his own
board for limited downloading and testing only.
- Users pad their u/d ratio by uploading false files.
- Program quality is that of a seven year old.
- Program is so buggy you have roaches crawling from the floppy slot.
- Your lawyer told you that you had to read every copyright
license in every archive posted on your board.
There is a better way.. and it is free for the cooperation.
SDN distributions are shareware programs, sent directly to SDN
International(sm) by the authors for worldwide distribution and
posting.
SDN distributions requires authors not to send pornography or items
either restricted in distribution by US Government agencies or
copyright limitations.
SDN distributions are required to be share-able with others under
the terms of the author's copyright license.
SDN distributions are secured with two tamper-proof and verifiable
seals for the peace of mind of the author, the sysop and the user.
SDN's FidoNet distributions are available in TIC format for
automatic receiving, tossing and FILES listing updating.
The SDN Project is in periodic contact authors and associations
to assure the best possible cooperation.
SDN's distribution in Fidonet charges no fee to anyone.
3. SYSTEM REQUIREMENTS
~~~~~~~~~~~~~~~~~~~~~~
SDN activity is automated file distribution among amateur and
professional netmail capable bulletin board systems using FidoNet
Technical Standards of communications. Distribution is divided
into many categories. You may choose to carry one, some or all of
the SDN areas. Requirements for SDN activity to be enjoyed by you
and others are few and simple.
- Receive your SDN files in form a reliable source.
FileGate, FileBone, Files-Coordinator, satellite, etc.
- Do not change the compression or contents in any way.
- Permanently post the SDN kit (SDN_KIT) and update versions
when revised by The SDN Project. It is the soul of
the continuation of the network.
- Carry the SDN echo message area (SDN_CONF) echo.
- Let other sysops in your area know you carry SDN and make it
freely available to them.
4. ORIGIN OF SDN FILES
~~~~~~~~~~~~~~~~~~~~~~
Origination (Hatching) of SDN files is from the SDN Project BBS in
Connecticut, USA - only. The packaging format use by SDN is
copyrighted. The packaging format of SDN netmailing packets can
not be duplicated, changed or modified in any way when en route or
posted for downloading.
No one is allowed to hatch any files whatsoever into SDN
"TIC" areas.
5. SDN FILES FORMAT
~~~~~~~~~~~~~~~~~~~
SDN distributions are in a ready downloadable archive compressed
with ZIP 2.4g or later, with an .zip extension. These are the
compressed program files, just as they were received directly from
the author for public distribution. Following BBS conventions they
are given a name to reflect the program they contain and it's
version. These files can be decompressed into the separate
original program files.
Each file is secured for authentication with two forms of
proprietary seals. Secured first with Zip -AV security specific
for SDN's use, they are secured secondly with SDNSeal(c) that can
be tested using SDNTest(c). SDNSeal has never been hacked.
Any recompression, conversion, tampering or hacking in any way
voids these security seals, verification will not be passed,
rendering them no longer SDN files, they should not be posted or
passed on.
Inside each distributed archive is an SDN.ID file. The SDN.ID
format is also copyrighted. It is a full ASCII text description of
the program written by the author or compiled by SDN.
Example of Zip Archive Listing for watts20.zip
Length Method Size Ratio Date Time CRC-32 Attr Name
------ ------ ----- ----- ---- ---- -------- ---- ----
400 DeflatX 267 34% 11-01-95 00:00 ad6791e8 --w- FILES_ID.DIZ
1416 DeflatX 330 77% 11-01-95 00:00 f4a8a1b1 --w- REGISTER.FRM
806 DeflatX 502 38% 11-01-95 05:15 cc1eb5db --w- SDN.ID
9386 DeflatX 4019 58% 11-01-95 00:00 8fb3305f --w- WATTS.DOC
54983 DeflatX 39699 28% 11-01-95 00:00 b2a494bb --w- WATTS.EXE
------ ------ --- -------
66991 44817 34% 5
6. FILE ECHO AREAS
~~~~~~~~~~~~~~~~~~
In Fidonet, SDN files are distributed with accompanying .TIC
processing files. With the proper utilities each SDN file can be
fully processed and automatically integrated online.
Here is the usual step of events in receiving SDN files via
Fidonet.
- .ZIP and .TIC files arrive from your SDN feed.
- SDN.ID is extracted and posted to message base.
- File is tossed to the proper download directory.
- FILES.BBS listing updated with online description.
- Further mail processing for any downlinks.
Upon arrival into your INBOUND mail area, the SDN.ID description
file can be extracted from inside the archive by PKunzip. You are
extracting them out of the archive for separate posting and not
deleting them from inside.
These should be the first batch processing your mail calls to
process inbound mail. This example uses the MAKEMSG Fidonet
text->msg utility.
--- ONE.BAT ---
:START
FOR %%a IN (*.ARJ) DO CALL TWO.BAT %%a
:END
-------------------
--- TWO.BAT ---
:START
PKUNZIP e %1 sdn.id
MAKEMSG -$ -F"Sysop" -S1:141/840 -Csdn.id -Dd:\echo\public
DEL sdn.id
:END
------------------
Next you can run whatever other processing you do to inbound mail.
7. EXAMPLE TIC.CFG
~~~~~~~~~~~~~~~~~~
The following is one way to set up your SDN areas using Barry
Geller's popular program TICK. The example entries are SDN areas
in a TIC.CFG file.
-- TIC.CFG --
AREA D:\DOSTEXT 1-TEXT
1:141/840 PASS *C
1:141/865 TERRA H
AREA D:\DOSBUSI 1-BUIS
1:141/840 PASS *C ( <- the node you receive SDN from)
1:141/865 TERRA H ( <- the node you forward SDN to)
etc..
-------------
8. ECHO CONFERENCE AND REGISTRATION
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
There is only one SDN echo mail conference. The tag for your mail
processor is SDN_CONF. Obtain this area from wherever you obtain
your SDN file echo feed. If you are getting your SDN areas from
Planet Connect satellite, set up this conference on your system and
send replies on your return call to Planet Connect. If you are
getting SDN files via Pagesat satellite or Internet linkage.. ask
your net's Files_Coordinator or Files_Distribution node or around
your neck of the woods to see it you can link into the conference
somewhere locally. You should know how to set this up so I will
not bore you. Configure the area for REAL NAMES only.
SDN_CONF is used for many purposes. Chat regarding SDN or
Shareware programs in general. Important notices from the SDN
Project on files and SDN activity.
When you initially set up your SDN areas and join the SDN File
Echos, take a bit of time to let us know your BBS is linked in.
Many author's and users often ask me 'where are SDN files posted?'.
Just pop me off a message in SDN_CONF telling me you have joined.
(TO: Ray Kaliss)
In this echo I will also pre-announce all software I process for
distribution by placing a short description in the echo. In this
way you can tell what programs to expect to receive during the next
seven days and know that you might have missed one if you have not
received it from your feed by two weeks. You can then FileRequest
it to complete your load.
9. LINKING INTO SDN
~~~~~~~~~~~~~~~~~~~
There are a number of means available for sysops to network into
SDN distribution channels.
The first place any sysop should look to link into SDN activity is
with their own local nets Files_Coordinator or Files_Distribution
node. Most nets should have one by now. These nodes are usually
linked to either the FileBone or FileGate file flow.
You can browse the nodelist in Zone 1 for the USDN flag some SDN
sites use. Be aware that many regions and some zones do not allow
user flags.
A satellite link in Fido form, can be obtained through the
commercial service of Planet Systems Inc. or Pagesat.
We are also available via Internet for them that knows how :)
10. NETMAIL TO 1:141/840
~~~~~~~~~~~~~~~~~~~~~~~~
If you contact me by netmail at Fidonet 1:141/840 .. be aware I
could go broke answering all my netmail.. but I try. So use the
SDN_CONF echo area to contact me. If you must use netmail then
wait three or four days, and then poll me for a reply on hold.
Have fun!
*ray
SDN Project Manager
/eof